Skip to content

Add support for zwave_js controller firmware updates#15515

Merged
bramkragten merged 5 commits into
home-assistant:devfrom
raman325:controller_firmware
Feb 22, 2023
Merged

Add support for zwave_js controller firmware updates#15515
bramkragten merged 5 commits into
home-assistant:devfrom
raman325:controller_firmware

Conversation

@raman325
Copy link
Copy Markdown
Contributor

@raman325 raman325 commented Feb 20, 2023

Proposed change

Adds support for manual zwave_js controller firmware updates in the UI. Depends on the following PRs:

Will move this out of draft when the ready PRs are merged as it will likely require a merge conflict fix before this can be used and requires some additional logic to handle this #15517 as the controller node should not have this option in this UI

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue or discussion:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

];
const actions: DeviceAction[] = [];

if (!nodeStatus.is_controller_node) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this extra if, if we are only adding actions when not is_controller_node

Copy link
Copy Markdown
Contributor Author

@raman325 raman325 Feb 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we are adding actions if there is a controller node just for the firmware update but all of these actions come before the firmware update action in the list

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this possibly the confusing part because I moved the not operator outside of each individual check? I can move it back inside so each individual statement is easier to understand: https://github.com/home-assistant/frontend/pull/15515/files#diff-4834eb73ab93f8dfa87c03847b42ab8539d6b51909e48038a784dc80d08e2472R103-R106

bramkragten
bramkragten previously approved these changes Feb 21, 2023
@raman325
Copy link
Copy Markdown
Contributor Author

@kpine tested all three PRs E2E and everything looks functional!

@kpine
Copy link
Copy Markdown
Contributor

kpine commented Feb 22, 2023

Demo (file selection dialog omitted for privacy):

chrome_uRgy2A6IrN.mp4

Notice the version changes from 7.18.1 to 7.18.2 at the end.

@raman325 raman325 force-pushed the controller_firmware branch from 294eebc to 95d021b Compare February 22, 2023 02:28
@raman325
Copy link
Copy Markdown
Contributor Author

FYI I created some new strings for controller specific text, moved some stuff out of render that doesnt need to be there, and rebased. The result of the changes are in @kpine 's comment

@bramkragten bramkragten merged commit 19d721f into home-assistant:dev Feb 22, 2023
@raman325 raman325 deleted the controller_firmware branch February 22, 2023 17:01
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants